…sfile

Rebuild #23's gitignore feature under the CTO-chosen GLOBAL design: rig owns
ONE marker-delimited block in git's global core.excludesfile so the harness's
throwaway **/.claude/worktrees/ is ignored in EVERY repo on the machine, with
zero per-repo commits and no per-repo `rig apply`.

Wired like the git-hooks dispatcher (a `git config --global` setting + a
managed file), in the GLOBAL rig layer. Target resolution at apply time:
honor an existing core.excludesfile; when unset, set it to ~/.config/git/ignore
AND write the block there (so a clean machine is fully provisioned by `rig
init` alone). Reuses #23's marker reconcile machine (create/update/ok/conflict/
io_error), retargeted, plus:
  - strict idempotency: a re-apply is a byte-identical no-op;
  - dedup of the managed region: several duplicated blocks collapse to one,
    preserving user content BETWEEN blocks (splice per marker-pair, not
    first-begin..last-end);
  - drift in the GLOBAL section flags a missing/divergent/duplicated block and
    an unset core.excludesfile rig would set.

Default ON at plan level (an absent `gitignore` key still provisions), so the
GLOBAL block is NOT scaffolded into committed repo rig.yaml. The canonical
block text (markers + fixed comment + entry) is byte-identical to what a
provisioned machine already has, making re-apply zero-churn.

Review: ran multi-model `review` on this diff; addressed findings (interleaved
user-line preservation, XDG isolation in tests, scaffold cleanup, doc fixes).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…sfile (supersedes #23) (#29)

* feat(rig): provision .claude/worktrees ignore via global core.excludesfile

Rebuild #23's gitignore feature under the CTO-chosen GLOBAL design: rig owns
ONE marker-delimited block in git's global core.excludesfile so the harness's
throwaway **/.claude/worktrees/ is ignored in EVERY repo on the machine, with
zero per-repo commits and no per-repo `rig apply`.

Wired like the git-hooks dispatcher (a `git config --global` setting + a
managed file), in the GLOBAL rig layer. Target resolution at apply time:
honor an existing core.excludesfile; when unset, set it to ~/.config/git/ignore
AND write the block there (so a clean machine is fully provisioned by `rig
init` alone). Reuses #23's marker reconcile machine (create/update/ok/conflict/
io_error), retargeted, plus:
  - strict idempotency: a re-apply is a byte-identical no-op;
  - dedup of the managed region: several duplicated blocks collapse to one,
    preserving user content BETWEEN blocks (splice per marker-pair, not
    first-begin..last-end);
  - drift in the GLOBAL section flags a missing/divergent/duplicated block and
    an unset core.excludesfile rig would set.

Default ON at plan level (an absent `gitignore` key still provisions), so the
GLOBAL block is NOT scaffolded into committed repo rig.yaml. The canonical
block text (markers + fixed comment + entry) is byte-identical to what a
provisioned machine already has, making re-apply zero-churn.

Review: ran multi-model `review` on this diff; addressed findings (interleaved
user-line preservation, XDG isolation in tests, scaffold cleanup, doc fixes).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* test(rig): global-excludes unit tests, smoke leg, schema docs

- tests/test_global_excludes.py: target resolution both ways (core.excludesfile
  set vs unset, with injected git-config seams so no test runs real `git config
  --global`), every reconcile state, STRICT byte-identical re-apply, the
  dedup-of-managed-region collapse (incl. preserving a user line between blocks),
  CRLF/trailing-blank/no-final-newline preservation, drift parity, disabled-but-
  installed leftover scan, and a byte-stable canonical-block regression pin.
- conftest: autouse fixtures isolate HOME + XDG_CONFIG_HOME and stub the
  git-config read/write seams suite-wide, so a full-plan e2e test can never
  touch the real ~/.gitignore or real global git config.
- smoke.sh: HOME-isolated leg exercises the real init/apply flow — asserts
  core.excludesfile is set to the XDG default, the block is written, and the
  block is byte-stable (markers=2) across a re-apply. Also makes the mcp leg
  conditional on the carrier and prefers `uv run pytest`.
- docs/config-schema.md: the `gitignore` (global core.excludesfile) section and
  validation note.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>